CruiseControl [.Net] vs TeamCity for continuous integration?
Posted
by zappan
on Stack Overflow
See other posts from Stack Overflow
or by zappan
Published on 2008-10-12T18:45:18Z
Indexed on
2010/03/13
10:05 UTC
Read the original article
Hit count: 1005
continuous-integration
|teamcity
|cruisecontrol
|cruisecontrol.net
|build-automation
i would like to ask you which automated build environment you consider better, based on practical experience. i'm planning to do some .Net and some Java development, so i would like to have a tool that supports both these platforms.
i've been reading around and found out about CruiseControl.NET, used on stackoverflow development, and TeamCity with its support for build agents on different OS-platforms and based on different programming languages. so, if you have some practical experience on both of those, which one you prefer and why.
currently, i'm mostly interested in the ease of use and management of the tool, much less in the fact that CC is open source, and TC is a subject to licensing at some point when you have much projects to run (because, i need it for a small amount of projects).
also, if there is some other tool that meets the above-mentioned and you believe it's worth a recommendation - feel free to include it in the discussion.
© Stack Overflow or respective owner